home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.19990725-20000114
/
000462_news@columbia.edu _Fri Jan 14 02:55:15 2000.msg
< prev
next >
Wrap
Internet Message Format
|
2020-01-01
|
3KB
Return-Path: <news@columbia.edu>
Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.59.30])
by watsun.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id CAA26687
for <kermit.misc@watsun.cc.columbia.edu>; Fri, 14 Jan 2000 02:55:15 -0500 (EST)
Received: (from news@localhost)
by newsmaster.cc.columbia.edu (8.8.5/8.8.5) id CAA17724
for kermit.misc@watsun.cc.columbia.edu; Fri, 14 Jan 2000 02:30:33 -0500 (EST)
X-Authentication-Warning: newsmaster.cc.columbia.edu: news set sender to <news> using -f
Subject: Re: MS-DOS Kermit, more capabalities
From: cangel@famvid.com
Message-ID: <66Af4.3341$0l4.96678@tw12.nn.bcandid.com>
Organization: bCandid - Powering the world's discussions - http://bCandid.com
Date: Fri, 14 Jan 2000 07:19:31 GMT
To: kermit.misc@columbia.edu
On 1900-01-13 jrd@cc.usu.edu(JoeDoupnik) said:
JD> Newsgroups: comp.protocols.kermit.misc
--8<--cut
JD> > While I have your attention: I've been compiling and fiddling with the
JD> > WATTCP package which claims to have a part of it's code inside MSKermit.
JD> Wattcp and MSK are now very different animals for TCP/IP work. That
JD> divergence started when Erick very generously offered his code to the
JD> project. The gulf spread very quickly very widely. Today there is little
JD> resemblence. The MSK TCP/IP stack is modern and robust, but it is not a
JD> library or other exportable form. Its internal applications, such as say
JD> the DHCP client, are also modern.
More reasons to view the source code. 8)
JD> > MSKermit is many times more stable than the demo apps that come with
JD> > the WATTCP source (operation online is `intermittent' with send being
JD> > exremely poor and receive seems locked into something less than 9k6).
JD> > MSKermit OTOH seems to move right along using the same packet driver
JD> > and achieves 90% of theoretical max transfers on a regular basis.
JD> The MSK code is designed to work solidly with Packet Drivers and Novell's
JD> ODI drivers. It's not a series of approximations. It is robust by design.
JD> > Question: could you direct me to any particular part of the WATTCP
JD> > based code in the MSKermit source that would reveal how MSKermit seems
JD> > to be so much better than the `original'?
I would be making a mistake to _not_ view the source code for MSKermit
considering all that you've said.
The problem is that one v315 is in BOO which I have no way to decipher and
the other is a UUE of over a meg.
Is there a binary archive of this source code anywhere that I can download or
am I going to need a way to decode a 1meg+ UUE? Why would the MSKermit source
code be in two ASCII formats when kermit itself has no problem doing binary
transfers nor do any other protocols I am of aware of since the '80s?
>
> , ,
> o/ Charles.Angelich \o ,
> <| @AngelFire.com |> __o/
> / > USA, MI < \ __\__